Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0972

reference: 462-tree-1
name: 0972
tree-preservation-order: undefined
462-tpo-1
uprn
address-text
point: POINT (-1.028245 50.882469)
geometry: MULTIPOLYGON (((-1.028146 50.882458,-1.028150 50.882478,-1.028164 50.882496,-1.028186 50.882510,-1.028213 50.882519,-1.028244 50.882522,-1.028275 50.882519,-1.028303 50.882511,-1.028325 50.882497,-1.028339 50.882479,-1.028345 50.882460,-1.028340 50.882441,-1.028326 50.882423,-1.028305 50.882409,-1.028277 50.882400,-1.028246 50.882396,-1.028216 50.882399,-1.028188 50.882408,-1.028165 50.882422,-1.028151 50.882439,-1.028146 50.882458)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL